:-( Something went wrong  A problem occurred while you were trying to use your mailbox

All,

I finally installed Exchange 2013 on Datacenter 2012 R2. My first try to access the setup I encountered the following messages

X-OWA-Error: Microsoft.Exchange.Data.Storage.ObjectNotFoundException X-OWA-Version: 15.0.847.32 X-FEServer: EXCHANGE001 X-BEServer: EXCHANGE001 Date: 4/18/2014 4:55:14 PM

I'm tried another browser and still have the same issue. what I can I do to correct

this problem?

April 18th, 2014 8:02pm

All,

I finally installed Exchange 2013 on Datacenter 2012 R2. My first try to access the setup I encountered the following messages

X-OWA-Error: Microsoft.Exchange.Data.Storage.ObjectNotFoundException X-OWA-Version: 15.0.847.32 X-FEServer: EXCHANGE001 X-BEServer: EXCHANGE001 Date: 4/18/2014 4:55:14 PM

I'm tried another browser and still have the same issue. what I can I do to correct

this problem?

Free Windows Admin Tool Kit Click here and download it now
April 18th, 2014 8:03pm

you may have to remove and re-build the OWA virtual directory.
April 19th, 2014 5:44am

Thanks for the reply but how do I rebuilt the OWA virtual directory? This is a new installation and I never had a online 365 accout as some post i have been reading mentioned. I'm new to Exchange so please forgive me for not knowing.

Free Windows Admin Tool Kit Click here and download it now
April 19th, 2014 4:17pm

Hi 

Did you try logging into outlook for the affected user  and see the results ?

Did you try for one more user or the issue is happening for just one user ?

You can run  Get-MailboxPermission  on the affected mailbox and see if there are any permissions missing

Also i would suggest you to run Test-MAPIConnectivity -server mailbox1 | fl and see the results

I think the mailbox might be missing few attributes like exchangemdb,home server etc

Try recreating a new mailbox in Exchange 2013 and see the results

April 20th, 2014 3:44am

Did you install Exchange 2013 SP1 or CU3 ...if not please upgrade them....Restart the server and check it again...Make sure all the service is up and running.

Try to access the owa using https:\\localhost\owa in the server...

Make sure the database is mounted state.

Try to create new mailbox and check it out..

Free Windows Admin Tool Kit Click here and download it now
April 21st, 2014 3:02pm

Any update on performing above action item..

April 22nd, 2014 9:18am

Hi,

Before rebuilding the OWA virtual directory, we can try to resolve the issue. and Id like to recommend the following troubleshooting:

  1. When do you find the error? Can you open the OWA login page? Does the issue happen on all users?
  2. Check your event log and find if there is any related error.
  3. Restart Exchange Active Directory Topology Service.

If you have any question, please feel free to let me know.

T

Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2014 12:47pm

There might be some mailboxes corruption.

So check the mailbox for the user and disable mailbox and re-enable the mailbox by using the following command.

Check first :

Get-mailbox

then [PS]>Disable-Mailbox -identity user@domain.com

        [PS]>Enable-Mailbox -identity user@domain.com

It should fix the issue.

Thanks

Sowel

   

November 12th, 2014 1:47pm

Hi

Did you solve this problema? I'm having the same problem and I can not find any solution

Thanks in advance!

Free Windows Admin Tool Kit Click here and download it now
January 10th, 2015 3:35am

Check the Authentication. In my case it was form based authentication on ECP virtual directory of one of the CAS server. I changed it to Windows Authentication and basic. It worked!
January 21st, 2015 6:13pm

Hi to all

Actually, the problem appear only for new users, I saw that when I crate a new user, it takes around 15 to 20 minutes to be ready I suspect this is for the replication, I spoke with the Active Directory staff, but they ask me for an evidence of this...

I thought about this, use "repadmin /showobjmeta ADServer "CN=user..." against every domain controller, but I'm not sure if this can help to show the problem of replication..

Any idea?

Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 7:38pm

Hi to all

I solved this, at least for my network.

I saw that when I create a new user, the error raise, checking the objetc against every DC, I noticied that only one DC has the information and the other don't, so if I fire manually the replication, it solve the problem.

Another thing that I done to avoid doing the replication was to exclude the DC that delays to get the user data:

Set-ExchangeServer -Identity <Server> -StaticExcludedDomainControllers <server>

In this way, the system use the other servers.

August 7th, 2015 2:19pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics